O impacto da adoção o dos modelos de maturidade TMMi e MPT.Br na gestão de projetos de software

Software quality is defined as a set of characteristics that the final product should satisfy to meeting the users needs. Despite the increase of its importance, especially in the last two decades, projects still fail frequently because they don’t deliver the required quality standards, making many systems quickly obsolete or useless. In this context, maturity models such as the CMM, CMMI and MPS.Br, at national level, were proposed to help companies evaluate and improve their software process. One problem with these models is that they don’t provide adequate attention to testing processes which represent one of the most expensive tasks of the life cycle of a system. This paper presents the results of a systematic review conducted to assess the state of art about TMMi and MPT.Br maturity models, proposed to cover the gap of traditional models regarding the testing process, and their impact in the management of software projects by organizations. The results presented in this article demonstrate that use of TMMi and MPT.Br in addition to other maturity models can bring significant improvements to organizations in the software projects managment, improving the quality of products developed and customer satisfaction.Sociedad Argentina de Informática e Investigación Operativ

O impacto da adoção o dos modelos de maturidade TMMi e MPT.Br na gestão de projetos de software

Software quality is defined as a set of characteristics that the final product should satisfy to meeting the users needs. Despite the increase of its importance, especially in the last two decades, projects still fail frequently because they don’t deliver the required quality standards, making many systems quickly obsolete or useless. In this context, maturity models such as the CMM, CMMI and MPS.Br, at national level, were proposed to help companies evaluate and improve their software process. One problem with these models is that they don’t provide adequate attention to testing processes which represent one of the most expensive tasks of the life cycle of a system. This paper presents the results of a systematic review conducted to assess the state of art about TMMi and MPT.Br maturity models, proposed to cover the gap of traditional models regarding the testing process, and their impact in the management of software projects by organizations. The results presented in this article demonstrate that use of TMMi and MPT.Br in addition to other maturity models can bring significant improvements to organizations in the software projects managment, improving the quality of products developed and customer satisfaction.Sociedad Argentina de Informática e Investigación Operativ

O impacto da adoção o dos modelos de maturidade TMMi e MPT.Br na gestão de projetos de software

Software quality is defined as a set of characteristics that the final product should satisfy to meeting the users needs. Despite the increase of its importance, especially in the last two decades, projects still fail frequently because they don’t deliver the required quality standards, making many systems quickly obsolete or useless. In this context, maturity models such as the CMM, CMMI and MPS.Br, at national level, were proposed to help companies evaluate and improve their software process. One problem with these models is that they don’t provide adequate attention to testing processes which represent one of the most expensive tasks of the life cycle of a system. This paper presents the results of a systematic review conducted to assess the state of art about TMMi and MPT.Br maturity models, proposed to cover the gap of traditional models regarding the testing process, and their impact in the management of software projects by organizations. The results presented in this article demonstrate that use of TMMi and MPT.Br in addition to other maturity models can bring significant improvements to organizations in the software projects managment, improving the quality of products developed and customer satisfaction.Sociedad Argentina de Informática e Investigación Operativ

Structural testing with use cases

Understanding how a user interacts with a system is important if the goal is to deliver a product that meets the user's needs. Use cases constitute a primary source of requirements in a user-centered perspective and are often utilized to derive acceptance tests. Given such a critical role in requirements engineering, we introduce a novel set of testing criteria based on the use case specification with a two-fold objective: to assess the quality of test cases derived from use cases and to test the use case specification itself. Differently from previous approaches, the novel set of testing criteria requires that structural elements of the use cases be exercised at least once. To support the application of the new set of testing criteria, a testing coverage tool, called UCT - Use Case Tester, was developed. A case study using UCT shows that the new testing criteria are able to evaluate the quality of a test data set as well as to detect faults in use case specifications.Facultad de Informátic

Vulnerability detection techniques and tools: a survey with members of agile teams in Brazil

There is little information on the adoption of agile methodologies in Latin America, and there is a percentage of professionals who receive little formal training. This article aims to identify and describe the interest of team members who use agile methods in software development in vulnerability detection techniques and tools (VDTT). To do so, a survey was proposed listing 18 techniques and tools that make up three well-known processes of secure software development, namely: McGraw Process, OWASP CLASP and Howard and Lipner\u27s activities. The survey was applied to 111 members of agile software development teams who have already deployed, are in the process of deploying, or are going to deploy vulnerability detection techniques and tools in the projects. The participants of the survey were: (1) requirements analysts; (2) software architects; (3) developers; and (4) testers. Some organizations have specific members of agile teams, such as security experts, scrum masters, product owners, and agile coaches. From the collected data it was possible, by means of statistical techniques like Fisher\u27s Exact Test and measures of Lambda and Gama associations, to identify relationships between interest in the use of VDTT and the adoption of agile methods and the adoption of software quality frameworks and services. Existe poca información sobre la adopción de metodologías ágiles en América Latina, y hay un porcentaje de profesionales que reciben poca formación formal. Este artículo tiene como objetivo identificar y describir el interés de los miembros del equipo que utilizan métodos ágiles en el desarrollo de software en técnicas y herramientas de detección de vulnerabilidades (TFDV). Para ello, se propuso una encuesta que enumera 18 técnicas y herramientas que componen tres conocidos procesos de desarrollo de software seguro, a saber: McGraw Process, OWASP CLASP y las actividades de Howard y Lipner. La encuesta se aplicó a 111 miembros de equipos de desarrollo de software ágil que ya se han implementado, están en proceso de implementación o van a implementar técnicas y herramientas de detección de vulnerabilidades en sus proyectos. Los participantes de la encuesta fueron: (1) analistas de requisitos; (2) arquitectos de software; (3) desarrolladores; y (4) probadores. Algunas organizaciones de la muestra tienen miembros específicos de equipos ágiles, como expertos en seguridad, Scrum Masters, propietarios de productos y coaches ágiles. A partir de los datos recopilados, fue posible utilizar técnicas estadísticas Fisher Exact Test y medidas de asociaciones Lambda y Gama para identificar relaciones entre el interés en el uso de TFDV y la adopción de métodos ágiles y la adopción de marcos de software y calidad de servicio. Há poucas informações sobre a adoção de metodologias ágeis na América Latina, e há um percentual de profissionais que recebem pouco treinamento formal. Este artigo visa identificar e descrever o interesse dos membros de equipes que usam métodos ágeis no desenvolvimento de software em técnicas e ferramentas de detecção de vulnerabilidades (TFDV). Para tanto, foi proposto um survey que lista 18 técnicas e ferramentas que compõem três conhecidos processos de desenvolvimento de software seguro, a saber: Processo de McGraw, OWASP CLASP e as atividades de Howard e Lipner. O survey foi aplicado a 111 membros de equipes de desenvolvimento ágil de software que já implantaram, estão em processo de implantação ou ainda vão implantar técnicas e ferramentas de detecção de vulnerabilidades nos projetos. Os participantes do survey foram: (1) analistas de requisitos; (2) arquitetos de software; (3) desenvolvedores; e (4) testadores. Algumas organizações da amostra possuem membros específicos de equipes ágeis, tais como especialistas em segurança, Scrum masters, product owners e agile coaches. A partir dos dados coletados foi possível por meio das técnicas estatísticas Fisher Exact Test e medidas de associações Lambda e Gama identificar relações entre interesse no uso de TFDV e a adoção de métodos ágeis e a adoção de frameworks de qualidade de software e serviços

Debugging visualization tools: a systematic review

Debugging is the task of locate and fix program bugs. Debugging activity is performed in the same way since 1960’s, when the first symbolic debuggers were introduced. Recently, visualization techniques have been proposed to represent program information during fault localization. However, none of them were introduced at industrial environments. This article presents a systematic review about visualization techniques for debugging. Despite the increasing number of studies in the area, visual debugging tools are not yet used in practice.Sociedad Argentina de Informática e Investigación Operativ

Depuração de programas baseada em informação de teste estrutural

Orientadores : Mario Jino, Jose Carlos MaldonadoTese (doutorado) - Universidade Estadual de Campinas, Faculdade de Engenharia Eletrica e de ComputaçãoDoutorad

Structural Testing with Use Cases

Understanding how a user interacts with a system is important if the goal is to deliver a product that meets the user's needs. Use cases constitute a primary source of requirements in a user-centered perspective and are often utilized to derive acceptance tests. Given such a critical role in requirements engineering, we introduce a novel set of testing criteria based on the use case specification with a two-fold objective: to assess the quality of test cases derived from use cases and to test the use case specification itself. Differently from previous approaches, the novel set of testing criteria requires that structural elements of the use cases be exercised at least once. To support the application of the new set of testing criteria, a testing coverage tool, called UCT- UseCaseTester,was developed. A case study using UCT shows that the new testing criteria are able to evaluate the quality of a test data set as well as to detect faults in use case specifications